Repository navigation
Conversation
… API - Phase AI: Agent token login, phase ai enable per harness, status, run and exec, the process environment, supported services, requests, the proxy CA, disable and the security model. - Phase AI relay: phase relay start, the sandbox bootstrap, and how sessions renew. - Phase AI control API: the local phase.invalid routes, kept in the CLI section, apart from the public API. - Commands: the ai section now covers the proxy commands, token login mentions Agent tokens, and relay start is added.
Each harness page now covers both skills: Connections through the Phase AI proxy (what phase ai enable installs for that harness, how commands use Phase, and the restart steps), and application secrets, which agents manage without reading values. The examples no longer ask agents to run phase run, import .env files, or read secret values, which the phase-cli-app-secrets skill forbids.
Deploying phase-docs with
|
| Latest commit: |
c8fc8bb
|
| Status: | ✅ Deploy successful! |
| Preview URL: | https://2b5b9228.phase-docs.pages.dev |
| Branch Preview URL: | https://docs-cli-agents.phase-docs.pages.dev |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Documents the CLI side of Agents. Console docs for Agents will follow separately, once the UI settles.
/cli/ai): logging in with an Agent token or your own login,phase ai enablefor each harness, how each harness uses Phase,status,runandexec, the process environment, supported services (AWS and PostgreSQL), requests and approvals, the proxy CA,disable, and the security model./cli/ai/relay):phase relay start, the sandbox bootstrap, and how relay sessions renew./cli/ai/control-api): the localphase.invalidAPI that Agents use behind the proxy. It sits in the CLI section, apart from the public API, and covers access, errors, every route, the request lifecycle, and headers on proxied traffic.aisection now covers the proxy commands,relay startis added, and token login mentions Agent tokens.phase-cli-ai-relayfor Connections andphase-cli-app-secretsfor app secrets. Examples that asked agents to runphase run, import.envfiles or read secret values are gone, because the new app-secrets skill forbids them.Before merging
These pages describe the Agents release of the CLI (phasehq/cli#322), which isn't out yet. Merge this once that CLI release ships, or the live docs will describe commands users don't have.
Testing
feat--agents, with the v1 Agent token change from feat(ai): accept key-bearing v1 Agent tokens cli#327) and the Console API.yarn dev, and the build's Markdown export converts them.